Skip to content

docs(admin): document share link URL behaviour with multiple trusted domains#14989

Merged
skjnldsv merged 1 commit into
masterfrom
fix/multi-hostname-share-link-urls
May 27, 2026
Merged

docs(admin): document share link URL behaviour with multiple trusted domains#14989
skjnldsv merged 1 commit into
masterfrom
fix/multi-hostname-share-link-urls

Conversation

@skjnldsv

Copy link
Copy Markdown
Member

☑️ Resolves

What and why

When multiple trusted_domains are configured, Nextcloud generates URLs
(share links, download links, notifications) using the hostname from the
incoming request. In split-horizon DNS or dual-access setups (internal
cloud.local + external cloud.example.com), share links created
internally contain the internal hostname and break for external users.

The fix (overwritehost + overwrite.cli.url) was already mentioned
elsewhere in the docs but the connection to this specific problem was never
made explicit. This adds a dedicated subsection to
reverse_proxy_configuration.rst explaining the behaviour and showing
the correct config.

🖼️ Screenshots

No visual/layout changes — prose and code block addition only.

✅ Checklist

  • I have built the documentation locally and reviewed the output
  • Screenshots are included for visual changes
  • I have not moved or renamed pages (or added a redirect if I did)
  • I have run codespell or similar and addressed any spelling issues

Comment thread admin_manual/configuration_server/reverse_proxy_configuration.rst
@github-actions

github-actions Bot commented May 21, 2026

Copy link
Copy Markdown
Contributor

📖 Documentation Preview

🔍 Open preview →

📄 1 changed documentation page

Last updated: Wed, 27 May 2026 09:03:45 GMT

Comment thread admin_manual/configuration_server/reverse_proxy_configuration.rst Outdated
…domains

When multiple trusted_domains are configured, generated URLs (share links,
download links, notifications) use the hostname from the incoming request.
This is a common source of confusion for admins running split-horizon DNS
or dual internal/external access, as share links created internally contain
the internal hostname and break for external users.

Add a new subsection to reverse_proxy_configuration.rst explaining the
behaviour and showing how to force a canonical hostname via overwritehost
and overwrite.cli.url.

Fixes #11623

Signed-off-by: skjnldsv <skjnldsv@protonmail.com>
@skjnldsv skjnldsv force-pushed the fix/multi-hostname-share-link-urls branch from 7701c17 to 47e2077 Compare May 27, 2026 08:50
@skjnldsv skjnldsv requested review from artonge and come-nc May 27, 2026 08:52
@skjnldsv

Copy link
Copy Markdown
Member Author

Done @artonge and @come-nc

@skjnldsv skjnldsv merged commit 5e6cc3e into master May 27, 2026
28 checks passed
@skjnldsv skjnldsv deleted the fix/multi-hostname-share-link-urls branch May 27, 2026 12:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Impact of using multiple hostnames (on share links)

3 participants